-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add ability for plugins to be fetched from authenticated URLs #2896
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd personally prefer this as a CLI option over a header which is way more discoverable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 to Ryan's flag suggestion 👍
8d0bd82
to
7e4e060
Compare
updated the PR to use a cli flag. |
7e4e060
to
0904173
Compare
The second commit message says "use cli flag along with env var" but I think it actually removes the env var. Would it be worth rewording the commit message not to imply that the env var is still meant to work? |
@itowlson I will address the changes and squash the PR with the commit changes as well. |
Signed-off-by: karthik2804 <[email protected]>
0904173
to
d29ad4c
Compare
I believe the failing CI is unrelated to the changes here. |
This PR enables users to set a
SPIN_PLUGIN_AUTH_HEADER
environment variable that will then be set on the outgoing request. For example, the header would have a value liketoken <gh_token>
to get a plugin from a private repo.If this would be better served as a flag like `spin plugins install <secret_plugin> --auth-header "token <gh_token>", I would be happy to update this PR.